Position location message flows

ABSTRACT

Techniques for initiating and, if desired, modifying location services for Secure User Plane Location (SUPL) and other location architectures are described. To initiate SUPL service, a SUPL Location Platform (SLP) transmits a SUPL initial session message applicable to any service request to a SUPL enabled terminal (SET) and receives in response the service capabilities of the SET. The SLP selects and requests service from the SET consistent with the service capabilities of the SET. The SET may initiate SUPL service by requesting the service capabilities of the SLP. The SET selects and requests service from the SLP that is consistent with the service capabilities received from the SLP. The SET and SLP communicate to determine a position estimate for the SET. The service may be modified before or while communicating between the SET and the SLP to determine a position estimate for the SET.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. application Ser. No.13/081,396, filed Apr. 6, 2011, entitled “SUPL 3.0 Concept”, whichclaims the benefit of and priority under 35 USC 119 to U.S. ProvisionalApplication No. 61/322,823, filed Apr. 10, 2010, entitled “SUPL 3.0Concept, Procedures and Message Flows”, U.S. Provisional Application No.61/323,692, filed Apr. 13, 2010, entitled “SUPL 3.0 Concept, Proceduresand Message Flows”, and U.S. Provisional Application No. 61/328,017,filed Apr. 26, 2010, entitled “SUPL 3.0 Concept, Procedures and MessageFlows”, all of which are assigned to the assignee hereof and all ofwhich are incorporated herein by reference in their entireties.

BACKGROUND

It is often desirable, and sometimes necessary, to know the location orposition of a wireless device in a network. The terms “location” and“position” are synonymous and are used interchangeably herein. Forexample, a user may utilize the wireless device to browse through awebsite and may click on location sensitive content. A web server maythen query the network for the position of the wireless device. Thenetwork may initiate position processing with the wireless device inorder to ascertain the position of the wireless device. The network maythen return a position estimate for the wireless device to the webserver, which may use this position estimate to provide appropriatecontent to the user. There are many other scenarios in which knowledgeof the position of the wireless device is useful or necessary.

A message flow (which may also be called a call flow or a procedure) istypically executed in order to obtain a position estimate for thewireless device and to send this position estimate to a client entity,e.g., the web server. Various messages are typically exchanged betweenone or more network entities, the wireless device, and the client entityfor the message flow. These messages ensure that each entity is providedwith pertinent information, or can obtain this information from anotherentity, in order to carry out positioning for the wireless device and/orto deliver the position estimate to the client entity. However, thesemessages add to the traffic among the various network entities. Theadditional traffic may be especially great for location services inwhich a position estimate for the wireless device is periodicallyprovided to the client entity. The messages may also extend the responsetime for sending the position estimate to the client entity.Furthermore, different types of location service (e.g. provision of asingle location estimate, provision of a location estimate at fixedperiodic intervals, provision of a location estimate whenever sometrigger condition is encountered) may be associated with different typesof message flow which may add cost and complexity to the support ofmultiple types of location service.

One commonly used protocol for location based services is known asSecure User Plane Location (SUPL) 2.0. In the SUPL 2.0 protocol,assistance and positioning data is sent over the user's traffic channelusing a secure connection between the SUPL enabled Terminal (SET) andthe SUPL Location Platform (SLP) on the network side. While SUPL 2.0 isa secure means to efficiently provide location based services,improvements are desirable.

SUMMARY

Techniques for initiating and, if desired, modifying location servicesfor Secure User Plane Location (SUPL) and other location architecturesare described. To initiate SUPL service, a SUPL Location Platform (SLP)transmits a SUPL initial session message applicable to any servicerequest to a SUPL enabled terminal (SET) and receives in response theservice capabilities of the SET. The SLP selects and requests servicefrom the SET consistent with the service capabilities of the SET. TheSET may initiate SUPL service by requesting the service capabilities ofthe SLP. The SET selects and requests service from the SLP that isconsistent with the service capabilities received from the SLP. The SETand SLP communicate to determine a position estimate for the SET. Theservice may be modified before or while communicating between the SETand the SLP to determine a position estimate for the SET.

In one implementation, a method includes receiving from a Secure UserPlane Location (SUPL) agent a request for at least one position estimatefor a SUPL enabled terminal (SET); transmitting at least one User planeLocation Protocol (ULP) service layer message to the SET and receivingat least one ULP service layer message from the SET, wherein ULP servicelayer messages do not contain any positioning related parameters exceptpositioning protocol identification and positioning protocol messages;transmitting at least one positioning layer message to the SET andreceiving at least one positioning layer message from the SET, whereinpositioning layer messages conform to a positioning protocol that doesnot contain any service related parameters; and communicating with theSET to determine the at least one position estimate for the SET; andsending the at least one position estimate to the SUPL agent.

In one implementation, an apparatus includes at least one processorconfigured to: receive from a Secure User Plane Location (SUPL) agent arequest for at least one position estimate for a SUPL enabled terminal(SET); transmit at least one User plane Location Protocol (ULP) servicelayer message to the SET and receive at least one ULP service layermessage from the SET, wherein ULP service layer messages do not containany positioning related parameters except positioning protocolidentification and positioning protocol messages; transmit at least onepositioning layer message to the SET and receive at least onepositioning layer message from the SET, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; communicate with the SET to determine the atleast one position estimate for the SET; and send the at least oneposition estimate to the SUPL agent.

In one implementation, an apparatus includes means for receiving from aSecure User Plane Location (SUPL) agent a request for at least oneposition estimate for a SUPL enabled terminal (SET); means fortransmitting at least one User plane Location Protocol (ULP) servicelayer message to the SET and receiving at least one ULP service layermessage from the SET, wherein ULP service layer messages do not containany positioning related parameters except positioning protocolidentification and positioning protocol messages; means for transmittingat least one positioning layer message to the SET and receiving at leastone positioning layer message from the SET, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; and means for communicating with the SET todetermine the at least one position estimate for the SET; and means forsending the at least one position estimate to the SUPL agent.

In one implementation, a computer-readable medium including program codestored thereon, includes program code to receive from a Secure UserPlane Location (SUPL) agent a request for at least one position estimatefor a SUPL enabled terminal (SET); program code to transmit at least oneUser plane Location Protocol (ULP) service layer message to the SET andreceive at least one ULP service layer message from the SET, wherein ULPservice layer messages do not contain any positioning related parametersexcept positioning protocol identification and positioning protocolmessages; program code to transmit at least one positioning layermessage to the SET and receive at least one positioning layer messagefrom the SET, wherein positioning layer messages conform to apositioning protocol that does not contain any service relatedparameters; and program code to communicate with the SET to determinethe at least one position estimate for the SET; and program code to sendthe at least one position estimate to the SUPL agent.

In one implementation, a method includes receiving from a Secure UserPlane Location (SUPL) agent a request for at least one position estimatefor a SUPL enabled terminal (SET); transmitting at least one User planeLocation Protocol (ULP) service layer message to a SUPL LocationPlatform (SLP) and receiving at least one ULP service layer message fromthe SLP, wherein the ULP service layer messages do not contain anypositioning related parameters except positioning protocolidentification and positioning protocol messages; transmitting at leastone positioning layer message to the SLP and receiving at least onepositioning layer message from the SLP, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; communicating with the SLP to determine theat least one position estimate for the SET; and communicating with theSLP to provide to the SUPL agent at least one position estimate for theSET.

In one implementation, an apparatus includes at least one processorconfigured to: receive from a Secure User Plane Location (SUPL) agent arequest for at least one position estimate for a SUPL enabled terminal(SET); transmit at least one User plane Location Protocol (ULP) servicelayer message to a SUPL Location Platform (SLP) and receive at least oneULP service layer message from the SLP, wherein ULP service layermessages do not contain any positioning related parameters exceptpositioning protocol identification and positioning protocol messages;transmit at least one positioning layer message to the SLP and receiveat least one positioning layer message from the SLP, wherein positioninglayer messages conform to a positioning protocol that does not containany service related parameters; communicate with the SLP to determinethe at least one position estimate for the SET; and communicate with theSLP to provide to the SUPL agent at least one position estimate for theSET.

In one implementation, an apparatus includes means for receiving from aSecure User Plane Location (SUPL) agent a request for at least oneposition estimate for a SUPL enabled terminal (SET); means fortransmitting at least one User plane Location Protocol (ULP) servicelayer message to a SUPL Location Platform (SLP) and receiving at leastone ULP service layer message from the SLP, wherein the ULP servicelayer messages do not contain any positioning related parameters exceptpositioning protocol identification and positioning protocol messages;means for transmitting at least one positioning layer message to the SLPand receiving at least one positioning layer message from the SLP,wherein positioning layer messages conform to a positioning protocolthat does not contain any service related parameters; means forcommunicating with the SLP to determine the at least one positionestimate for the SET; and means for communicating with the SLP toprovide to the SUPL agent at least one position estimate for the SET.

In one implementation, a computer-readable medium including program codestored thereon, includes program code to receive from a Secure UserPlane Location (SUPL) agent a request for at least one position estimatefor a SUPL enabled terminal (SET); program code to transmit at least oneUser plane Location Protocol (ULP) service layer message to a SUPLLocation Platform (SLP) and receive at least one ULP service layermessage from the SLP, wherein ULP service layer messages do not containany positioning related parameters except positioning protocolidentification and positioning protocol messages; program code totransmit at least one positioning layer message to the SLP and receiveat least one positioning layer message from the SLP, wherein positioninglayer messages conform to a positioning protocol that does not containany service related parameters; program code to communicate with the SLPto determine the at least one position estimate for the SET; and programcode to communicate with the SLP to provide to the SUPL agent at leastone position estimate for the SET.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 shows a network architecture capable of providing locationservices for SUPL enabled terminals (SETs).

FIG. 2 shows a network architecture that includes a visited/servingnetwork, a home network, and a requesting network.

FIG. 3 illustrates another view of the SUPL ULP architecture withseparated service and positioning layers.

FIG. 4 illustrates a conventional SUPL ULP architecture with intertwinedservice and positioning layers.

FIG. 5 is a flow chart illustrating a SUPL positioning process that maybe performed by the SLP.

FIG. 6 is a flow chart illustrating a SUPL positioning process that maybe performed by the SET.

FIG. 7 shows an embodiment of a generalized message flow.

FIG. 8 shows an embodiment of a message flow for a network initiatedsingle fix service.

FIG. 8A illustrates an example of a SUPL INIT message that may be usedwith the message flows of FIGS. 8, 9, 12, and 13.

FIG. 9 shows an embodiment of a message flow for a network initiatedtriggered periodic service.

FIG. 10 shows an embodiment of a message flow for a SET initiated singlefix service.

FIG. 11 shows an embodiment of a message flow for a SET initiatedtriggered periodic service.

FIG. 12 shows an embodiment of a message flow for a network initiatedsingle fix LPP service with SET assisted A-GNSS.

FIG. 13 shows an embodiment of a message flow for a network initiatedsingle fix TIA-801 service with SET assisted A-GNSS.

FIG. 14 shows an embodiment of a message flow for a SET initiated singlefix LPP service with SET assisted A-GNSS.

FIG. 15 shows an embodiment of a message flow for a SET initiated singlefix TIA-801 service with SET assisted A-GNSS.

FIG. 16 shows a block diagram an embodiment of the SET, SLP, andcommunication network in network architectures illustrated in FIGS. 1and 2.

DETAILED DESCRIPTION

The techniques described herein may be used for various wirelessnetworks such as Code Division Multiple Access (CDMA) networks, TimeDivision Multiple Access (TDMA) networks, Frequency Division MultipleAccess (FDMA) networks, Orthogonal FDMA (OFDMA) networks, networkssupporting a combination of the aforementioned technologies, networkswith wireless wide area network (WWAN) coverage and/or wireless localarea network (WLAN) coverage, a wireless personal area network (WPAN). ACDMA network may implement one or more radio access technologies (RATs)such as Wideband-CDMA (W-CDMA), cdma2000, and so on. Cdma2000 coversIS-2000, IS-856, and IS-95 standards. A TDMA network may implement oneor more radio technologies such as Global System for MobileCommunications (GSM), Digital Advanced Mobile Phone System (D-AMPS) orsome other RAT. D-AMPS covers IS-136 and IS-54. These various radiotechnologies and standards are known in the art. W-CDMA and GSM aredescribed in documents from an organization named “3rd GenerationPartnership Project” (3GPP). Cdma2000 is described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). 3GPPand 3GPP2 documents are publicly available. A WLAN may be an IEEE802.11x network, and a WPAN may be a Bluetooth network, an IEEE 802.15x,or some other type of network. The techniques may also be implemented inconjunction with any combination of WWAN, WLAN and/or WPAN. Thetechniques may also be used to help locate a device communicating usinga wireline IP capable network such as a network providing DSL or cableaccess and/or may be used to support client devices communicating usinga wireline network.

The techniques may also be used for various location architectures suchas user plane architectures. A user plane is a mechanism for carryingdata for higher-layer applications and employing a user-plane bearer,which is typically implemented with protocols such as User DatagramProtocol (UDP), Transmission Control Protocol (TCP), and InternetProtocol (IP), all of which are known in the art. Messages supportinglocation services and positioning are carried as part of data in a userplane architecture. The techniques may be used for Secure User PlaneLocation (SUPL) and pre-SUPL architectures promulgated by Open MobileAlliance (OMA), a 3GPP control plane architecture described in 3GPP TS23.271, TS 43.059, and TS 25.305, a 3GPP2 control plane architecturedescribed in IS-881 and 3GPP2 X.S0002, a 3GPP2 user plane architecturedescribed in X.S0024, and so on. For clarity, the techniques aredescribed below for Secure User Plane Location (SUPL).

FIG. 1 shows a network architecture 100 capable of providing locationservices for SUPL enabled terminals (SETs). A SET is a device capable ofcommunicating with SUPL capable entities that support positioning andlocation services for SETs. For simplicity, only one SET 120 is shown inFIG. 1. SET 120 may be stationary or mobile and may also be called amobile station (MS), a user equipment (UE), a terminal, a station, asubscriber unit, or some other terminology. SET 120 may be a cellularphone, a personal digital assistant (PDA), a wireless modem, a personalcomputer, a laptop computer, a telemetry device, a tracking device, andso on. For example, SET 120 may be a UE in Universal MobileTelecommunication System (UMTS), an MS in GSM or cdma2000, a personalcomputer in an IP-based network, and so on.

SET 120 may include a SUPL agent 122 capable of accessing SUPL capableentities. SET 120 may also be a target SET, which is a SET whoseposition is being sought by a SUPL agent that may be internal orexternal to the SET. SET 120 may perform functions such as privacy,security, positioning measurement and position calculation for locationservices.

SET 120 may communicate with a communication network 130 for variousservices such as voice, packet data, messaging, and so on. SET 120 mayalso communicate with SUPL capable entities via network 130. Network 130may be a wireless network such as a cdma2000 network, an LTE network, aUMTS network, a GSM network, some other radio access network (RAN), aWLAN, and so on. Network 130 may also be a wireline network such as anIP-based network, a phone network, a cable network, and so on. In somecases, network 130 may comprise multiple individual networks (e.g. anLTE network and a separate UMTS network each connected to the Internet).In such a case, SET 120 and H-SLP 150 may connect to differentnetworks—e.g. SET 120 may connect to an LTE network whereas H-SLP mayconnect to a UMTS network. SET 120 may also receive signals from one ormore satellites 190, which may be part of the Global Positioning System(GPS), the European Galileo system, the Russian Glonass system, or someother satellite positioning system. For example, the techniques providedherein may be applied to or otherwise enabled for use in variousregional systems, such as, e.g., Quasi-Zenith Satellite System (QZSS)over Japan, Indian Regional Navigational Satellite System (IRNSS) overIndia, Beidou over China, etc., and/or various augmentation systems(e.g., an Satellite Based Augmentation System (SBAS)) that may beassociated with or otherwise enabled for use with one or more globaland/or regional navigation satellite systems. By way of example but notlimitation, an SBAS may include an augmentation system(s) that providesintegrity information, differential corrections, etc., such as, e.g.,Wide Area Augmentation System (WAAS), European Geostationary NavigationOverlay Service (EGNOS), Multi-functional Satellite Augmentation System(MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo AugmentedNavigation system (GAGAN), and/or the like. Thus, as used herein an SPSmay include any combination of one or more global and/or regionalnavigation satellite systems and/or augmentation systems, and SPSsignals may include SPS, SPS-like, and/or other signals associated withsuch one or more SPS.

SET 120 may measure signals from satellites 190 and/or base stations innetwork 130 and may obtain pseudo-range measurements for the satellitesand network measurements from the base stations. The pseudo-rangemeasurements may be used to derive a position estimate for SET 120.

A Home SUPL Location Platform (H-SLP) 150 is responsible for SUPLservice management and position determination. Normally, a SET (e.g. SET120) will have a single H-SLP (e.g. H-SLP 150) which is provided by thehome network operator for the SET user. In addition to H-SLPs, there arealso E-SLPs (emergency service SLPs, which support determining thelocation of a SET when there is an emergency call), V-SLPs (Visited SLP,which may assist the H-SLP to obtain the SET location when the SET isnot served by the home network), and D-SLPs (Discovered SLP which wouldtypically be associated with a visited network and not the home networkand may provide location services to the SET without involving the H-SLP150). In FIG. 1, H-SLP 150 represents an H-SLP, but it may alsorepresent a D-SLP or E-SLP and thus, H-SLP 150 is sometimes referred tosimply as SLP 150. SUPL service management may include managinglocations of SETs and storing, extracting, and modifying locationinformation of target SETs. H-SLP 150 includes a SUPL Location Center(SLC) 152 and typically includes a SUPL Positioning Center (SPC) 154.SLC 152 performs various functions for location services, coordinatesthe operation of SUPL, and interacts with SETs over user plane bearer.SLC 152 may perform functions for privacy, initiation, security, roamingsupport, charging/billing, service management, position calculation, andso on. SPC 154 supports positioning for SETs, is responsible formessages and procedures used for position calculation, and supportsdelivery of assistance data to the SETs. SPC 154 may perform functionsfor security, assistance data delivery, reference retrieval, positioncalculation, and so on. An SPC may have access to GPS receivers (areference network, perhaps a global one) and may receive signals forsatellites so that it can provide assistance data.

A SUPL agent (e.g., SUPL agent 122 or 170) is a function or an entitythat obtains location information for a target SET. In general, a SUPLagent may reside in a network entity (e.g., SUPL agent 170) or a SET(e.g., SUPL agent 122) or may be external to both the network and theSET. In the case of a SET resident SUPL agent, the SUPL Agent may or maynot access network resources to obtain the location information and, asin SET-based mode, positioning and resource access from the network maynot be one-for-one (e.g. a SET may use resources obtained once from thenetwork to support location determination at several different times). Anetwork resident SUPL agent may utilize Mobile Location Servicesapplications (MLS Apps) to access an H-SLP or a requesting network,which includes a Requesting SLP (R-SLP) that supports location servicesfor SUPL agents. An MLS application is an application that requests andconsumes location information. Location information may be anyinformation related to location and may comprise various types ofposition estimate (e.g., latitude and longitude coordinates, latitudeand longitude with an expected error estimate, etc). MLS coversinteraction between a SUPL agent and an H-SLP, R-SLP, D-SLP or E-SLP,whereas SUPL covers interaction between an H-SLP, E-SLP, V-SLP or D-SLPand a SET.

FIG. 2 shows a network architecture 102 that includes a visited/servingnetwork 104, a home network 106, and a requesting network 108. Visitednetwork 104 includes a V-SLP 160. Home network 106 includes H-SLP 150that supports location services and positioning. Requesting network 108includes an R-SLP 162 that supports location services for SUPL agents.H-SLP 150, V-SLP 160, and R-SLP 162 each includes an SLC and may includean SPC, which operate as described above for FIG. 1. In someembodiments, the visiting network 104 with V-SLP 160 may be eliminated.

The SUPL entities in FIGS. 1 and 2 are similar to that described in U.S.application Ser. No. 11/510,332, filed Aug. 24, 2006, and entitled“Location Reporting with Secure User Plane Location (SUPL)”, withPublication No. US 2007/0182547, which is assigned to the assigneehereof and the entirety of which is incorporated herein by reference, aswell as document OMA-AD-SUPL-V2_(—)0-20060619-D, entitled “Secure UserPlane Location Architecture,” Draft Version 2.0, June 2006, which ispublicly available from OMA, which describe location based servicesknown as SUPL 2.0. The network entities in FIGS. 1 and 2 may also bereferred to by other names in other networks and other locationarchitectures. For example, in a 3GPP-based network (e.g., a UMTSnetwork), an SLC is called a Gateway Mobile Location Center (GMLC), anSPC is called a Serving Mobile Location Center (SMLC), a SET is called aUE, and a SUPL agent is called an LCS client. The functions andsignaling performed by the 3GPP entities are similar to those performedby the corresponding SUPL entities, thereby enabling comparable servicesand capabilities. In general, an SLC may be called a location center, anLCS server, a location server, a Mobile Positioning Center (MPC), and soon. An SPC may be called a positioning entity, a positioning center, aPosition Determination Entity (PDE), and so on. While SUPL 2.0 is knownas a secure means to efficiently provide location based services,improvements are desired. For example, the number of messages exchangedbetween participating entities to support a particular type of locationrequest might be reduced. In addition, a common message flow might beused for different types of location service that in SUPL 2.0 requiresupport of different message flows.

SUPL may support the following positioning methods (among others): SETassisted A-GPS, SET assisted A-GNSS, SET based A-GPS, SET based A-GNSS,Autonomous GPS or autonomous GNSS; Advanced forward link trilateration(A-FLT); SET assisted and/or SET based Enhanced observed time difference(EOTD); SET assisted and/or SET based Observed time difference ofarrival (OTDOA) for UMTS and/or for LTE; SET assisted and/or SET basedEnhanced cell/sector and cell-ID; SET assisted and/or SET based WiFipositioning, SET assisted and/or SET based Short Range Node (SRN)positioning and various SET assisted and/or SET based Hybridcombinations of these.

For a SET based mode, the position of the SET is determined by the SET,possibly with assistance data from an SPC. For a SET assisted mode, theposition of the SET is determined by the SPC with assistance (e.g.,measurements) from the SET. The autonomous GPS and GNSS methods and theA-GPS and A-GNSS methods derive a position estimate for the SET basedsolely on satellite measurements and have high accuracy. The hybridmethod derives a position estimate based on multiple position methodsand has high accuracy and high reliability if GPS and/or GNSS areincluded. The A-FLT, EOTD, and OTDOA methods derive a position estimatebased on measurements of base station timing made by the SET and havegood accuracy. The enhanced cell/sector and cell-ID methods derive aposition estimate based on known positions of cell/sectors of a cellularnetwork and have coarse accuracy. For the enhanced cell/sector method,the position estimate may also be derived based on network measurementssuch as radio signal timing and signal strengths. The WiFi and SRNmethods employ signal measurements from WiFi Access Points and shortrange nodes (e.g. Bluetooth) and normally have high accuracy. Thesevarious positioning methods are known in the art. The terms “positionestimate”, “location estimate”, and “position fix” are often usedinterchangeably. A position estimate may be given in absolutecoordinates (e.g., latitude and longitude), in relative coordinates(e.g. number of meters north and east of a known fixed location) or as acivic address (e.g. street address, city and country) or as somecombination of these and may provide the expected error (e.g. mayprovide a geographic area that represents possible locations of a SET).

SUPL may support various services, four of which are shown in Table 1.

TABLE 1 Location Service Description Immediate Provide locationinformation (e.g., the location of a location service target SET)immediately when requested. Deferred Provide location informationmultiple times based on location service periodic triggers or after aspecific event has occurred. Assistance Provide single, multiple orcontinuous assistance data data service transfer. SUPL Establishment ofsecure SUPL session context for connection service extended timeperiods.

Immediate location services may also be referred to as networkinitiated, SET initiated, roaming, non-roaming, and so on. Deferredlocation services may include periodic and/or triggered services. Fortriggered services, the reporting of position estimates is determined bytriggers or a trigger mechanism that indicates when to report the SETlocation to a SUPL agent. The triggers may be determined by the SUPLagent, sent to the H-SLP, and then forwarded to the target SET. Periodictriggers for periodic triggered service may comprise a periodicinterval, the number of position reports, and a possible start time tobegin reporting. Triggers may be related to area events, a change in thelocation or velocity of a SET or to other conditions. Area eventtriggers for area event triggered service may correspond to the SETentering, leaving or remaining within a predefined geographic area.Triggers related to a change in the location or velocity of a SET maycorrespond to the SET location, velocity or acceleration changing bypredefined thresholds. Triggers may also be combined such that thelocation of a SET is only obtained when two or more trigger conditionshave occurred or when only one of several alternative triggers hasoccurred. Additional or other services may also be supported.

Location services may be categorized as shown in Table 2.

TABLE 2 Location Service Description Network initiated Services thatoriginate from the network, with the (NI) services SUPL agent residingin or having access to the network. SET initiated Services thatoriginate from the SET, with the SUPL (SI) services agent residingwithin or having access to the SET.

Network initiated may also be referred to as mobile terminated. SETinitiated may also be referred to as mobile originated.

SUPL supports two communication modes between a SET and an SLP forpositioning with an SPC. Table 3 summarizes the two communication modes.

TABLE 3 Communication Mode Description Proxy mode The SPC does not havedirect communication with the SET, and the SLC acts as a proxy betweenthe SET and the SPC. Non-proxy The SPC has direct communication with theSET. mode

SUPL supports roaming and non-roaming for a SET. Table 4 summarizesseveral roaming and non-roaming modes.

TABLE 4 Roaming/Non-roaming Description Non-roaming The SET is withinthe service area of its H-SLP. Roaming with The SET is outside theservice H-SLP positioning area of its H-SLP, but the H-SLP stillprovides location functionality. Roaming with The SET is outside theservice V-SLP positioning area of its H-SLP, and a V-SLP provideslocation functionality

As used herein, roaming and non-roaming are with respect to SUPL, andnot with respect to communication network 130. Network 130 may havedifferent definition and criteria on roaming and non-roaming, which arenot discussed herein.

The service area of an H-SLP is an area within which the H-SLP canprovide a position estimate for a SET or relevant assistance data to aSET without contacting other SLPs. When the SET is roaming, the H-SLPmay provide location functionality (e.g., position determination and SPCfunctionality) or may request a V-SLP to provide this locationfunctionality.

A set of message flows may be defined for each of the supported locationservices. Each message flow may be applicable for a specific locationservice and a specific set of conditions, e.g., proxy or non-proxy,roaming or non-roaming, network initiated or SET initiated, and so on. Aspecific message flow may be used to obtain the desired location servicefor the applicable conditions.

FIG. 3 illustrates another exemplary view of the architecture 100applicable to the SUPL User plane Location Protocol (ULP), which is theprotocol used by SUPL between a SET and an SLP. As can be seen in FIG.3, a service layer 124 and a positioning layer 126 are separated throughthe use of different ULP messages, where ULP service layer messagesbetween SET 120 and SLC 152 in SLP 150 are illustrated with a solid lineand ULP positioning messages between SET 120 and SLC 152 in SLP 1502 areshown with broken lines. As illustrated, the ULP services layer messagebetween SET 120 and SLC 152 in SLP 150 contains no positioningcomponents, so that all positioning related components are encapsulatedin the ULP positioning layer messages between SET 120 and SLC 152 in SLP150. Thus, ULP messages in the positioning layer in the SUPL ULParchitecture 100, while transported through the service layer, arecompletely transparent to the service layer and do not carry any servicelayer parameters. Similarly, ULP messages in the service layer do notconvey any parameters directly related to positioning (e.g. location id,requested assistance data, A-GNSS or A-GPS Fine Time Assistance (FTA),etc.). ULP messages in the positioning layer (e.g. SUPL POS, SUPL POSINIT) would normally convey embedded messages defined by a separatepositioning protocol such as LTE Positioning Protocol (LPP defined in3GPP TS 36.355), Radio Resource LCS Protocol (RRLP defined in 3GPP TS44.031), Radio Resource Control (RRC defined in 3GPP TS 25.331), IS-801known also as TIA-801 (defined in 3GPP2 TS C.S0022) or LPP combined withLPP extension (LPPe defined in OMA-TS-LPPe-V1 from OMA). In particular,except for conveying positioning protocol messages (e.g. for RRLP, RRC,LPP or IS-801), there are no positioning parameters in SUPL ULPmessages: all SUPL ULP parameters thus relate to the service layer andanything related to positioning falls under a separate positioningprotocol. This restriction separates the service and positioning layers.

As an alternative to the exemplary view of architecture 100 shown inFIG. 3, messages in the ULP positioning layer may be conveyed directlybetween positioning layer 126 in SET 120 and SPC 154 in SLP 150. In yetanother alternative, positioning layer 126 in SET 120 and SPC 154 in SLP150 might each exchange positioning protocol messages with service layer124 and SLC 152, respectively with service layer 124 and SLC 152exchanging these message inside ULP positioning messages (e.g. SUPL POS,SUPL POS INIT) exchanged between SET 120 and SLP 150 without being awareof the content of the positioning protocol messages.

In the SUPL 2.0 architecture defined by OMA, the architecture shown inFIG. 3 cannot be used, as SUPL 2.0 requires that some ULP messagesexchanged between service layer 124 in SET 120 and SLC 152 in SLP 150also carry positioning related parameters that are defined as part ofULP and not use a separate positioning protocol like RRLP, TIA-801 orLPP. This means that the services layer (solid arrow in FIG. 3) is nolonger separate from the positioning layer (broken arrow in FIG. 3) butinstead the layers (and hence the arrows) need to be combined in someway. One illustration of this is shown in FIG. 4

The SUPL ULP architecture 100 simplifies the ULP protocol and reducesthe number of call flows required for covering all use cases, relativeto known SUPL ULP architectures. In one embodiment, the SUPL ULParchitecture 100 may include one or more of the followingsimplifications: only proxy mode is supported; only one roaming model(roaming with H-SLP) is supported; and only LPP and TIA-801 aresupported as positioning protocols.

FIG. 5 is a flow chart 200 illustrating a SUPL positioning process thatmay be performed by the SLP 150 in SUPL ULP architecture 100. The SLP150 receives a request for a position estimate for the SET 120 from SUPLagent 170 (202). The SLP 150 transmits a SUPL session initiation messageto the SET 120 that is applicable to any service request (204). Thus,the initiation message may be the same for immediate location service ordeferred location service, such as a periodic or area event triggeredservice. This reduces the impacts to SET 120 and SLP 150 in supportingdifferent services since processing of the initiation message does notdepend on a particular service. In addition, new services can be addedlater to SUPL without affecting the initiation message (e.g. withoutrequiring a new or modified initiation message). Furthermore, becausethe initiation message does not need to indicate services orcapabilities, it can be a small message that may be easier to transferby some means of delivery such as SMS. In response, the SLP 150 receivesa request for a secure IP connection from SET 120 and, once thisconnection has been established, receives the service capabilities ofthe SET 120 (206). The SLP 150 selects and requests services from theSET 120 that are consistent with the service capabilities of the SET120, which activates the SUPL service delivery (208). The SLP 150 mayprovide the SLP service capabilities to the SET 120 in response toreceipt of the service capabilities of the SET 120. In one embodiment,no positioning parameters are provided prior to requesting service fromthe SET 120. Optionally, the SLP 150 may receive from the SET 120 aservice modification request, which has service parameters that aremodified with respect to the service requested from the SET 120 (210).The service modification request may support particular preferences ofthe SET user—e.g. a preference that any location estimate provided toSUPL Agent 170 be less accurate (i.e. have a higher probable error) thanthat requested by SLP 150 or that locations estimates that wererequested periodically by SLP 150 occur at a lower frequency than thatrequested. The service modification may also support temporarylimitations of SET 120—e.g. may reduce location accuracy or thefrequency of periodic location if SET 120 processor or memoryutilization is currently high. The SLP 150 communicates with the SET 120to determine at least one position estimate for the SET 120 during SUPLservice delivery (212). For example, the service may be an immediatelocation a single immediate position may be produced. If the service isfor deferred location, multiple positions may be periodically generatedor generated based on other trigger events. Optionally, the SLP 150 mayreceive from the SET 120, or send to the SET 120, a service modificationrequest, which has service parameters that are modified with respect tothe service requested from the SET 120 or subsequently modified by theSET (214). The one or more position estimates are sent to the SUPL agent170 (216).

FIG. 6 is a flow chart 300 illustrating a SUPL positioning process thatmay be performed by the SET 150 in SUPL ULP architecture 100. The SET120 receives a request for a position estimate for the SET 120 from SUPLagent 122 (302). The SET 120 establishes a secure IP connection to SLP150 and then requests the service capabilities from the SLP 150 to starta SUPL initiation session with the SLP 150 (304). The SET 120 mayprovide service capabilities of the SET 120 to the SLP 150 with therequest from the service capabilities of the SLP 150. The SET 120receives the service capabilities from the SLP 150 in response (306).The SET 120 selects and requests services from the SLP 150 that areconsistent with the service capabilities of the SLP 150, which activatesthe SUPL service delivery (308). In one embodiment, no positioningparameters are provided prior to requesting service from the SLP 150.Optionally, the SET 120 may receive from the SLP 150 a servicemodification request, which has service parameters that are modifiedwith respect to the service requested from the SLP 150 (310). Themodified service parameters may support preferences of the SLP 150service provider—e.g. may provide lower location accuracy or lessfrequent periodic location or less assistance data than was requested.The SET 120 communicates with the SLP 150 to determine at least oneposition estimate for the SET 120 during SUPL service delivery (312).For example, the service may be an immediate location a single immediateposition may be produced. If the service is for deferred location,multiple positions may be periodically generated or generated based onother trigger events. Optionally, the SET 120 may receive from the SLP150, or send to the SLP 150, a service modification request, which hasservice parameters that are modified with respect to the servicerequested from the SLP 150 or subsequently modified by SLP 150 (314).The SET 120 communicates with the SLP 150 to provide to the SUPL agent122 at least one position estimate for the SET 120 during the SUPLservice delivery session.

FIGS. 7-15 illustrate example call flows for the SUPL ULP architecture100. The flows for the SUPL ULP architecture 100 include support forexisting SUPL services including immediate single fix, triggeredperiodic service, and triggered area event service. The SUPL ULParchitecture 100 further includes support for other services, such asperiodic assistance data delivery. In general, the basic call flows forSUPL ULP architecture 100 consist of four primary building blocks:Capability Transfer, Service Activation, Service Delivery and ServiceTermination.

An optional extended call flow may include an additional building blockfor Service Modification. Service Modification may be used to permitbetter privacy, which is becoming an increasingly important requirementfor commercial location services For example, a SET 120 user may bewilling to be located by a SUPL Agent but may want to control the levelof service—e.g. location accuracy, duration and frequency of a periodicsession. Thus, rather than abort and later attempt to restart a session,Service Modification allows a session to continue at a maximum servicelevel that the user will accept. Service Modification may be performedmodification immediately after service activation to allow modificationof service parameters (not the service itself) based on privacyrequirements and positioning capabilities. Service Modification may alsobe used to modify an ongoing deferred location session—e.g. increase thefrequency of location for a navigation service when a user needs morefrequent and precise directions. Service Modification can reuseparameters defined for Service Activation and may be a simple extensionfrom a signaling perspective. The use of service modification permitsbetter privacy and more flexible service delivery.

The SUPL call flows provided herein use examples for single fix andtriggered periodic fix services in non-roaming mode, as well as examplesof LPP and TIA-801 call flows. The presented call flows are meant toillustrate the concept and do not contain details such as security,notification, etc.

FIG. 7 shows an embodiment of a generalized message flow 400 for theSUPL ULP architecture 100. The call flow includes three phases:Initiation, Delivery; and Termination. Initiation includes ServiceCapabilities Exchange (step B) and Service Activation (step C), as wellas a SUPL INIT initiation message from the SLP 150 to the SET 120 (stepA), which is only required for network initiated scenarios.Additionally, during the Initiation phase, an optional ServiceModification may be performed (step D). During Service CapabilitiesExchange, SUPL CAPABILITY TRANSFER messages may be exchanged between theSET 120 and SLP 150 to provide their respective service capabilitiesi.e., capabilities they are able and willing to support for the SUPLsession. During the Service Activation, a SUPL ACTIVATE message isprovided by the SET 120 (for a SET Initiated service request) or SLP 150(for a Network Initiated service request) to activate the SUPL serviceby requesting a service in line with their capabilities. During ServiceModification, a SUPL MODIFY message may be provided by the SLP 150 (fora SET Initiated service request) or SET 120 (for a Network Initiatedservice request) to request a service modification based on information(e.g. service parameters or the identity of the SUPL Agent) receivedduring Service Activation. As long as service is reduced and notincreased (e.g. via a request for lower rather than higher locationaccuracy or less frequent rather than more frequent periodic location),there is no need to acknowledge the serviced modification requestbecause it is certain that the recipient of the request can support areduced service.

During the Delivery phase, Service Delivery is performed (steps E, F andsteps H, I). Steps H and I are used for deferred location services (e.g.triggered periodic location delivery), and are not used for an immediatelocation service such as an immediate single fix. During ServiceDelivery, one or more SUPL POS messages are exchanged between SET 120and SLP 150 in step E and, for deferred location service, in step H todeliver the requested service (location information or assistance data).For deferred location services, one or more instances of step H mayoccur. In a SET initiated session, and where applicable, the SLP 150 mayreturn the position estimate (position) to the SET with a SUPL REPORTmessage (steps F and I). For deferred location services, one instance ofstep I may occur for each instance of step H. Additionally, during theDelivery phase, an optional Service Modification may be performed (stepG) at any point during Service Delivery. During Service Modification,SET 120 may send a request to SLP 150 or SLP 150 may send a request toSET 120 to change one or more parameters related to the service beingperformed—e.g. may request higher or lower location accuracy or a higheror lower frequency of location. If the request is to increase or improveservice (e.g. increase location accuracy or the frequency of periodiclocation), the recipient of a service modification request may return anacknowledgment if the new service can be supported.

During the Termination event, Service Termination is performed (stepsZ), during which the SUPL session is terminated by the SLP 150. Duringservice termination, the entity that initiated the service (either SET120 or SLP 150) may send a SUPL END to the other party.

As discussed above, the services layer is separate from the positioninglayer. Accordingly, exchanged messages, such as SUPL CAPABILITY TRANSFERmessage (step B), SUPL ACTIVATE message (step C), SUPL MODIFY (steps D,G) may include Service parameters but no positioning messages.Positioning protocol messages but no service related parameters may beencapsulated in other ULP messages, e.g., SUPL POS (step E and H). Toprovide extra flexibility, some service related messages (e.g. SUPLACTIVATE) may optionally carry positioning protocol messages that aretransparent to the service layer and transferred between SET positioninglayer 126 and SLC 154.

FIG. 8 shows an embodiment of a message flow 500 for a network initiatedsingle fix service. SLP 150 starts a Network Initiated SUPL session withSET 120 by sending a SUPL INIT message to SET 120 (step A). The SET 120may establish a secure IP connection to SLP 150 and provides its servicecapabilities (ProvServCap) (i.e., the services it is willing and able tosupport) and requests the SLP's service capabilities (ReqServCap) inSUPL CAPABILITY TRANSFER (step B). The SUPL CAPABILITY TRANSFER in stepB may also include the positioning protocols supported by SET 120. Inline with the service capabilities of SET 120, the SLP 150 selects andrequests the service (ReqService), in this case a single immediate fix,in SUPL ACTIVATE (which activates the SUPL service). The SLP alsoprovides its service capabilities (ProvServCap) and may also sendpositioning information within a positioning protocol message(PosPayload) (step C). The positioning information may include thepositioning capabilities of SLP 150, a request for the positioningcapabilities of SET 120, positioning assistance data or some combinationof these. The positioning protocol message in step C may correspond to apositioning protocol that SET 120 indicated it supports in step B. TheSET 120 evaluates the service request and, depending on furtherinformation received about the service requested (e.g., SUPL Agent ID,etc.), may optionally modify the service (e.g., different QoP) andreturns a modified service request (ReqService) with modified serviceparameters to the SLP in SUPL MODIFY (step D). The SET 120 may also sendpositioning information within a positioning protocol message(PosPayload) in SUPL MODIFY. The positioning information may include thepositioning capabilities of SET 120, some location measurements made bySET 120 or a request for positioning assistance data or some combinationof these. The SET 120 and SLP 150 engage in a SUPL POS sessionexchanging positioning protocol messages (PosPayload) contained withinone or more SUPL POS messages and SLP 150 obtains a position estimate(step E). The SLP 150 terminates the SUPL session (step F).

The SUPL INIT message sent in step A of FIG. 8 may need to be recognizedand partially decoded by a SET 120 that does not support the servicebeing invoked in FIG. 8—e.g. may need to be recognized and partiallydecoded by a SET 120 that supports an earlier version of SUPL such asSUPL 1.0 or SUPL 2.0. One reason would be to allow SET 120 to establisha secure IP connection to SLP 150 and then return a SUPL END message toterminate the SUPL session and indicate to SET 150 which version orversions of SUPL SET 120 supports. This SUPL END response is supportedin SUPL 1.0 and SUPL 2.0 but depends on a SET being able to decode aSUPL version number parameter in a SUPL INIT and, in the case of SUPL2.0, also being able to decode a minimum and maximum SUPL versionparameter. If SLP 150 receives in this SUPL END message the version ofSUPL supported by SET 120 it can restart the session using the sameversion of SUPL—which may then lead to a different message flow than theone shown in FIG. 8 but one that can partly or fully support the servicerequested by a SUPL Agent (e.g. SUPL Agent 170). In order to ensure thatSET 120 can always decode a SUPL INIT, SLP 150 may send a SUPL INIT instep A in FIG. 8 that contains the same mandatory parameters andpossibly some of the same optional parameters as defined for a SUPL INITmessage in SUPL 1.0 and SUPL 2.0. However, the version parameter in theSUPL INIT sent by SLP 150 in step A in FIG. 8 may indicate a higher SUPLversion number (e.g. the SUPL version for which the message flow in FIG.8 is valid). In addition, the SUPL INIT may contain an embedded messageor an embedded container (e.g. a new SUPL INIT defined for a higherversion of SUPL) that contains parameters applicable to the message flowin FIG. 8. For example, FIG. 8A illustrates an example of a SUPL INITmessage that may be used, which includes the SUPL Version 502, SUPL 1.0Parameters 504, SUPL 2.0 Parameters 506, as well as an embedded messageor embedded container 508, which may include higher version SUPLParameters. A SET 120 that supports this higher version of SUPL may thenignore some or all of the SUPL 1.0 and SUPL 2.0 parameters in the SUPLINIT and only interpret the parameters in the embedded message (orembedded container). Possibly the embedded message may contain noparameters in which case SET 120 may ignore some or all of the SUPL 1.0and SUPL 2.0 parameters and obtain necessary SUPL parameters from SLP150 in subsequent messages—e.g. in the message sent by SLP 150 in step Cin FIG. 8. A SET 120 that does not support the higher version of SUPLassociated with FIG. 8 will still recognize the SUPL INIT message and beable to decode the SUPL 1.0 and possibly SUPL 2.0 parameters as well asthe SUPL version number contained in the SUPL INIT in step A of FIG. 8.As SET 120 will not support this version of SUPL, it will return a SUPLEND message to SLP 150 indicating the version of SUPL that it doessupport. SLP 150 can then restart the session using the SUPL versionsupported by SET 120. The same type of SUPL INIT message as describedhere may also be sent in step A in FIG. 9, FIG. 12 and FIG. 13 in orderto support a SET 120 that either does or does not support the messageflows in each of these figures.

FIG. 9 shows an embodiment of a message flow 600 for a network initiatedtriggered periodic service. Initiation steps A through D in message flow600 are the same as steps A through D in message flow 500, except thatthe requested service (ReqService) in step C is for a triggered periodicservice. When the first position estimate is due, SET 120 and SLP 150engage in a SUPL POS session exchanging positioning protocol messages(PosPayload) contained within one or more SUPL POS messages and the SLP150 obtains a position estimate (and/or assistance data is delivered tothe SET 120) (step E). Either the SET 120 or the SLP 150 may modify theservice (i.e., service parameters), for example (QoP, interval betweenfixes, etc.) (step F). The SET 120 or SLP 150 may also include apositioning protocol message (PosPayload) in the SUPL MODIFY message(step F). The SET 120 and SLP 150 may engage in additional SUPL POSsessions exchanging position information as applicable (step G). The SLP150 terminates the SUPL session (step Z).

FIG. 10 shows an embodiment of a message flow 700 for a SET initiatedsingle fix service. If the SET 120 does not already have the servicecapabilities of the SLP 150 (e.g. as obtained by SET 120 in a previousSUPL session), the SET 120 starts the SUPL sessions by establishing asecure IP connection to SLP 150 and then sending a SUPL CAPABILITYTRANSFER message, providing its own service capabilities (ProvServCap)and requesting the SLP's service capabilities (ReqServCap) (step A). Ifstep A was executed, the SLP 150 provides its service capabilities(ProvServCap) to the SET in SUPL CAPABILITIES TRANSFER (step B). TheSUPL CAPABILITIES TRANSFER in step B may also include the positioningprotocols supported by SLP 150. The SET 120 activates the SUPL service,either after steps A and B are executed, or as the initial message ifSET 120 already had the service capabilities of the SPL 150 by sendingSUPL ACTIVATE (step C). The SET 120 selects and requests the service(ReqService) in line with the service capabilities of SLP 150 in SUPLACTIVATE. The SET 120 may also send positioning information within apositioning protocol message (PosPayload) in SUPL ACTIVATE (step C). Thepositioning information may include the positioning capabilities of SET120, some location measurements made by SET 120 or a request forpositioning assistance data or some combination of these. Thepositioning protocol message in step C may correspond to a positioningprotocol that SLP 150 indicated it supports in step B. The SLP 150evaluates the service request and, depending on further informationreceived about the service requested (e.g., SUPL Agent ID, etc.), theSLP 150 may modify the service (e.g., different QoP) by returning amodified service request (ReqService) with modified service parametersto the SET 120 in SUPL MODIFY (step D). The SLP 150 may also sendpositioning information (PosPayload) within a positioning protocolmessage in the SUPL MODIFY (step D). The positioning information mayinclude the positioning capabilities of SLP 150 and/or positioningassistance data (e.g. as requested by SET 120 in step C). The SET 120and SLP 150 engage in a SUPL POS session exchanging positioning protocolmessages (PosPayload) contained within one or more SUPL POS messages(step E). The SLP 150 terminates the SUPL session and, if the positionestimate was calculated at the SLP 150, sends the position estimate(position) to the SET 120 (step F).

FIG. 11 shows an embodiment of a message flow 800 for a SET initiatedtriggered periodic service. Initiation steps A through D in message flow800 are the same as steps A through D in message flow 700, except thatthe requested service (ReqService) in step C is for a triggered periodicservice. When the first position estimate is due, SET 120 and SLP 150engage in a SUPL POS session exchanging positioning information withinpositioning protocol messages (PosPayload) contained within one or moreSUPL POS messages and the SLP 150 obtains a position estimate (and/orassistance data is delivered to the SET 120) (step E). Where applicable,the SLP 150 returns the position estimate (position) to the SET 120 andmay also or instead send position information (e.g. positioningassistance data) in a positioning protocol message (PosPayload) in SUPLREPORT (step F). Either the SET 120 or the SLP 150 may modify theservice (i.e., service parameters), for example (QoP, interval betweenfixes, etc.) (step G). The SET 120 or SLP 150 may also include positioninformation (e.g. assistance data or a request for assistance data) in apositioning protocol message (PosPayload) in the SUPL MODIFY message(step G). The SET 120 and SLP 150 may engage in additional SUPL POSsessions exchanging position information and the SLP 150 may returnposition estimates to SET 120 in SUPL REPORT as applicable (steps H andI). The SLP 150 terminates the SUPL session (step Z).

FIG. 12 shows an embodiment of a message flow 900 for a networkinitiated single fix service where the positioning protocol is LPP andthe position method is SET assisted A-GNSS. SLP 150 starts a NetworkInitiated SUPL session with SET 120 by sending a SUPL INIT message toSET 120 (step A). The SET 120 establishes a secure IP connection to SLP150 and then provides its service capabilities (ProvServCap) (i.e., theservices it is willing and able to support) and requests the SLP'sservice capabilities (ReqServCap) in SUPL CAPABILITY TRANSFER (step B).The SUPL CAPABILITY TRANSFER in step B may include the positioningprotocols supported by SET 120 which in this example will include LPP.In line with the service capabilities of SET 120, the SLP 150 selectsand requests the service (ReqService), in this case a single immediatefix, in SUPL ACTIVATE (which activates the SUPL service). The SLP alsoprovides its service capabilities (ProvServCap) and includes an LPPmessage that requests the SET's LPP positioning capabilities (LPPReqCap) and may also include an LPP message that includes positioninginformation (PosPayload) such as assistance data (step C). The LPPmessage in step C corresponds to the LPP positioning protocol that SET120 may have indicated it supports in step B. The SET 120 evaluates theservice request and, depending on further information received about theservice requested (e.g., SUPL Agent ID, etc.), may optionally modify theservice (e.g., different QoP) and returns a modified service request(ReqService) with modified service parameters to the SLP in SUPL MODIFY(step D). The SET 120 may also include in the SUPL MODIFY message one ormore LPP messages (PosPayload) that provide one or more of its LPPpositioning capabilities (LPP ProvCap), location information containinglocation measurements (LPP ProvLocInfo) and a request for certainassistance data (LPP ReqAssistData). If step D is not executed, SET 120may instead include one or more LPP messages containing one or more ofits LPP positioning capabilities, some location measurements and arequest for certain assistance data in a SUPL POS message (step E). TheSLP 150 sends one or more LPP messages containing assistance data (LPPProvAssistData) and/or a request for Location Information (LPPReqLocInfo) in a SUPL POS message (step F). The SET 120 returns an LPPmessages containing location information, in this case GNSS Pseudo Rangemeasurements, (LPP ProvLocInfo) within a SUPL POS message to the SLP 150and the SLP 150 calculates a position estimate (step G). The SLP 150terminates the SUPL session (step H). Once the service has beenactivated at step C, the positioning layer (in this case LPP) canoperate mostly independently of the service layer in steps E, F and G(or D, F and G if step D is performed). The positioning layer LPPmessages and their transport within particular service layer messagescan be different than show in this example. For example, positioninglayer messages could be TIA-801 or LPP plus LPPe.

FIG. 13 shows an embodiment of a message flow 1000 for a networkinitiated single fix TIA-801 service with SET assisted A-GNSS. SLP 150starts a Network Initiated SUPL session with SET 120 by sending a SUPLINIT message to SET 120 (step A). The SET 120 establishes a secure IPconnection to SLP 150 and then provides its service capabilities(ProvServCap) (i.e., the SUPL services it is willing and able tosupport) and requests the SLP's service capabilities (ReqServCap) inSUPL CAPABILITY TRANSFER (step B). The SUPL CAPABILITY TRANSFER in stepB may also include the positioning protocols supported by SET 120 whichin this example include TIA-801. In line with the service capabilitiesof SET 120, the SLP 150 selects and requests the service (ReqService),in this case a single immediate fix, in SUPL ACTIVATE (which activatesthe SUPL service). The SLP also provides its service capabilities(ProvServCap) and may include one or more TIA-801 positioning layermessages that request the SET's positioning capabilities (TIA-801ReqCap) and/or provide positioning information (step C). The TIA-801message in step C corresponds to the TIA-801 positioning protocol thatSET 120 may have indicated it supports in step B. The SET 120 evaluatesthe service request and, depending on further information received aboutthe service requested (e.g., SUPL Agent ID, etc.), may optionally modifythe service (e.g., different QoP) and returns a modified service request(ReqService) with modified service parameters to the SLP in SUPL MODIFY(step D). The SET 120 includes within the SUPL MODIFY one or morepositioning layer TIA-801 messages (PosPayload) containing the TIA-801positioning capabilities of SET 120 (MS INFO), location information(Prov PP) and a request for GNSS acquisition assistance (Req AA) andsensitivity assistance (Req SA). If step D is not executed, the TIA-801messages (PosPayload) described for step D may be provided instead in aSUPL POS message (step E). The SLP 150 returns one or more TIA-801position layer messages (PosPayload) in a SUPL POS message containingGNSS acquisition assistance (Prov AA), sensitivity assistance (Prov SA)and a request for GNSS pseudo range information (Req PR) (step F). TheSET 120 obtains the requested GNSS pseudo range measurements and returnsa TIA-801 positioning layer message containing location information (inthis case GNSS Pseudo Range measurements) to the SLP 150 (Prov PR) andthe SLP 150 calculates a position estimate (step G). The SLP 150terminates the SUPL session (step H). Once the service has beenactivated at step C, the positioning layer (in this case TIA-801) canoperate mostly independently of the service layer in steps E, F and G(or D, F and G if step D is performed). The positioning layer TIA-801messages and their transport within particular service layer messagescan be different than show in this example.

FIG. 14 shows an embodiment of a message flow 1100 for a SET initiatedsingle fix service where the positioning protocol is LPP and theposition method is SET assisted A-GNSS. If the SET 120 does not alreadyhave the service capabilities of the SLP 150 (e.g. as obtained by SET120 in a previous SUPL session), the SET 120 starts the SUPL session byestablishing a secure IP connection to SLP 150 and then sending a SUPLCAPABILITY TRANSFER, providing its own service capabilities(ProvServCap) and requesting the SLP's service capabilities (ReqServCap)(step A). If step A was executed, the SLP 150 provides its servicecapabilities (ProvServCap) to the SET in SUPL CAPABILITIES TRANSFER(step B). The SUPL CAPABILITIES TRANSFER in step B may also include thepositioning protocols supported by SLP 150 which in this example includeLPP. The SET 120 activates the SUPL service, either after steps A and Bare executed, or as the initial message if SET 120 already had theservice capabilities of the SPL 150 by sending SUPL ACTIVATE (step C).The SET 120 selects and requests the service (ReqService) in line withthe service capabilities of SLP 150, in this case single immediate fix,in SUPL ACTIVATE. The SET 120 may also include in the SUPL ACTIVATEmessage one or more LPP positioning layer messages (PosPayload) thatprovide one or more of its positioning capabilities (LPP ProvCap),location information containing location measurements (LPP ProvLocInfo)and a request for certain assistance data (LPP ReqAssistData) (step C).The LPP messages in step C correspond to the LPP positioning protocolthat SLP 150 may have indicated it supports in step B. The SLP 150evaluates the service request and, depending on further informationreceived about the service requested (e.g., SUPL Agent ID, etc.), theSLP 150 may modify the service (e.g., different QoP) by returning amodified service request (ReqService) with modified service parametersto the SET 120 in SUPL MODIFY (step D). The SLP 150 may include in theSUPL MODIFY messages one or more LPP positioning layer messages(PosPayload) containing assistance data (LPP ProvAssistData) and/or arequest for location information (LPP ReqLocInfo). If step D is notexecuted, SLP 150 may instead include one or more LPP messages(PosPayload) in a SUPL POS message containing assistance data (LPPProvAssistData) and/or a request for location information (LPPReqLocInfo) (step E). The SET 120 obtains the requested locationinformation (in this case GNSS pseudo range measurements) and sends anLPP positioning layer message (PosPayload) in a SUPL POS message to SLP150 containing this location information (LPP ProvLocInfo) and the SLP150 calculates a position estimate (step F). The SLP 150 terminates theSUPL session and sends the position estimate (position) to SET 120 in aSUPL END (step G). Once the service has been activated at step C, thepositioning layer (in this case LPP) can operate mostly independently ofthe service layer in steps E, and F (or D and F if step D is performed).The positioning layer LPP messages and their transport within particularservice layer messages can be different than show in this example. Forexample, positioning layer messages could be TIA-801 or LPP plus LPPe.

FIG. 15 shows an embodiment of a message flow 1200 for a SET initiatedsingle fix service where the positioning protocol is TIA-801 and theposition method is SET assisted A-GNSS. If the SET 120 does not alreadyhave the service capabilities of the SPL 150 (e.g. as obtained by SET120 in a previous SUPL session), the SET 120 starts the SUPL session byestablishing a secure IP connection to SLP 150 and then sending a SUPLCAPABILITY TRANSFER, providing its own service capabilities(ProvServCap) and requesting the SLP's service capabilities (ReqServCap)(step A). If step A was executed, the SLP 150 provides its servicecapabilities (ProvServCap) to the SET in SUPL CAPABILITIES TRANSFER(step B). The SUPL CAPABILITIES TRANSFER in step B may also include thepositioning protocols supported by SLP 150 which in this example includeTIA-801. The SET 120 activates the SUPL service, either after steps Aand B are executed, or as the initial message if SET 120 already had theservice capabilities of the SPL 150 by sending SUPL ACTIVATE (step C).The SET 120 selects and requests the service (ReqService) in line withthe service capabilities of SLP 150, in this case single immediate fix,in SUPL ACTIVATE. The SET 120 may also include in the SUPL ACTIVATEmessage one or more TIA-801 positioning layer messages (PosPayload) thatprovide one or more of its positioning capabilities (Prov MS INFO),location information (Prov PP) and a request for acquisition assistance(Req AA) and sensitivity assistance (Req SA) (step C). The TIA-801messages in step C correspond to the TIA-801 positioning protocol thatSLP 150 may have indicated it supports in step B. The SLP 150 evaluatesthe service request and, depending on further information received aboutthe service requested (e.g., SUPL Agent ID, etc.), the SLP 150 maymodify the service (e.g., different QoP) by returning a modified servicerequest (ReqService) with modified service parameters to the SET 120 inSUPL MODIFY (step D). The SLP 150 may include in the SUPL MODIFYmessages one or more TIA-801 positioning layer messages (PosPayload),containing acquisition assistance (Prov AA), sensitivity assistance(Prov SA) and a request for pseudo range information (Req PR). If step Dis not executed, SLP 150 may instead send a SUPL POS message containingthe same TIA-801 messages (PosPayload) described in step D (step E). TheSET 120 obtains the requested GNSS pseudo range measurements and sendsone or more TIA-801 positioning layer messages (PosPayload) in a SUPLPOS message to SLP 150 containing this location information (Prov PR)and a request for a location result (Req LocRes) (step F). The SLP 150calculates a position estimate and sends it to SET 120 in TIA-801message (Prov LocRes) inside a SUPL END to terminate the SUPL session(step G). Once the service has been activated at step C, the positioninglayer (in this case TIA-801) can operate mostly independently of theservice layer in steps E, and F (or D and F if step D is performed). Thepositioning layer TIA-801 messages and their transport within particularservice layer messages can be different than shown in this example.

The SUPL service exemplified in FIGS. 7 to 15 differs from how servicesare supported in SUPL 2.0. There may be an advantage in aligning theSUPL service exemplified in FIGS. 7 to 15 with SUPL 2.0. For example,this may reduce the amount of software, firmware and hardwareimplementation necessary to support the SUPL service exemplified inFIGS. 7 to 15 when software, firmware and hardware is already availablefor SUPL 2.0. To help achieve this alignment, SUPL parameters thatsupport services (e.g. SUPL immediate location, SUPL periodic location,SUPL triggered location) that appear the same to a SUPL Agent 112 or 170in both the SUPL service exemplified in FIGS. 7 to 15 and SUPL 2.0 maybe used without change in both versions of SUPL. Alternatively, theseparameters may be defined and/or encoded differently in both versions ofSUPL but may carry exactly the same information. As an example, SUPLparameters (such as a geographic area and a trigger condition of a SETentering, staying within or leaving the area) that convey the triggeringconditions for a SUPL triggered service may be reused without change inboth versions of SUPL or the information from these parameters may beretained without change although the parameters encoding thisinformation may be different. In the former case, alignment would occurat the coding level whereas in the latter case the alignment would be atthe information level.

FIG. 16 shows a block diagram an embodiment of SET 120, H-SLP 150, andcommunication network 130 in network architectures 100 and 102 in FIGS.1 and 2. Communication network 130 provides communication for terminalsand may include base stations (or Node Bs) and network controllers. Forsimplicity, FIG. 16 shows only one processor 1920, one memory unit 1922,and one transceiver 1924 for SET 120, only one processor 1930, onememory unit 1932, one transceiver 1934, and one communication (Comm)unit 1936 for network 130, and only one processor 1940, one memory unit1942, and one transceiver 1944 for SLP 150. In general, each entity mayinclude any number of processors, memory units, transceivers,communication units, controllers, and so on. SET 120 may supportwireless communication and may also receive and process GPS signals.

On the downlink, base stations in network 130 transmit traffic data,signaling, and pilot to terminals within their coverage area. Thesevarious types of data are processed by processor 1930 and conditioned bytransceiver 1934 to generate a downlink signal, which is transmitted viaan antenna. At SET 120, the downlink signals from one or more basestations are received via an antenna, conditioned by transceiver 1924,and processed by processor 1920 to obtain various types of informationfor location services. For example, processor 1920 may decode messagesused for the message flows described above. Memory units 1922 and 1932store program codes and data for SET 120 and network 130, respectively.On the uplink, SET 120 may transmit traffic data, signaling, and pilotto one or more base stations in network 130. These various types of dataare processed by processor 1920 and conditioned by transceiver 1924 togenerate an uplink signal, which is transmitted via the SET antenna. Atnetwork 130, the uplink signals from SET 120 and other terminals arereceived and conditioned by transceiver 1934 and further processed byprocessor 1930 to obtain various types of information (e.g., data,signaling, reports, and so on). Network 130 communicates with SLP 150and other network entities via communication unit 1936.

Within SLP 150, processor 1940 performs processing for the SLP, memoryunit 1942 stores program codes and data for the SLP, and communicationunit 1944 allows the SLP to communicate with network 130 and othernetwork entities. Processor 1940 may perform processing for SLP 150 forthe message flows described above.

The techniques described herein may be implemented by various means. Forexample, the techniques may be implemented in hardware, firmware,software, or a combination thereof. For a hardware implementation, theunits used to perform the processing at each entity may be implementedwithin one or more application specific integrated circuits (ASICs),digital signal processors (DSPs), digital signal processing devices(DSPDs), programmable logic devices (PLDs), field programmable gatearrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. The software codes may be stored in amemory unit (e.g., memory unit 1922, 1932 or 1942 in FIG. 16) andexecuted by a processor (e.g., processor 1920, 1930 or 1940). The memoryunit may be implemented within the processor or external to theprocessor. As used herein the term “memory” refers to any type of longterm, short term, volatile, nonvolatile, or other memory and is not tobe limited to any particular type of memory or number of memories, ortype of media upon which memory is stored.

If implemented in firmware and/or software, the functions may be storedas one or more instructions or code on a non-transitorycomputer-readable medium. Examples include computer-readable mediaencoded with a data structure and computer-readable media encoded with acomputer program. Computer-readable media includes physical computerstorage media. A storage medium may be any available medium that can beaccessed by a computer. By way of example, and not limitation, suchcomputer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to store desired programcode in the form of instructions or data structures and that can beaccessed by a computer; disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

Although the present invention is illustrated in connection withspecific embodiments for instructional purposes, the present inventionis not limited thereto. Various adaptations and modifications may bemade without departing from the scope of the invention. Therefore, thespirit and scope of the appended claims should not be limited to theforegoing description.

What is claimed is:
 1. A method comprising: receiving from a Secure UserPlane Location (SUPL) agent a request for at least one position estimatefor a SUPL enabled terminal (SET); transmitting at least one User planeLocation Protocol (ULP) service layer message to the SET and receivingat least one ULP service layer message from the SET, wherein ULP servicelayer messages do not contain any positioning related parameters exceptpositioning protocol identification and positioning protocol messages;transmitting at least one positioning layer message to the SET andreceiving at least one positioning layer message from the SET, whereinpositioning layer messages conform to a positioning protocol that doesnot contain any service related parameters; and communicating with theSET to determine the at least one position estimate for the SET; andsending the at least one position estimate to the SUPL agent.
 2. Themethod of claim 1, wherein the positioning layer messages areencapsulated within the ULP service layer messages, wherein the ULPservice layer messages do not contain service layer parameters.
 3. Themethod of claim 1, wherein the positioning layer messages areencapsulated within the ULP service layer messages, wherein the ULPservice layer messages contain service layer parameters.
 4. The methodof claim 1, wherein the positioning protocol comprises LTE PositioningProtocol (LPP), Radio Resource LCS Protocol (RRLP), Radio ResourceControl (RRC) or IS-801.
 5. The method of claim 1, wherein nopositioning related parameters are provided prior to requesting servicefrom the SET.
 6. The method of claim 1, further comprising determining aposition estimate for the SET for multiple reporting events.
 7. Themethod of claim 1, wherein transmitting the at least one ULP servicelayer message to the SET and receiving the at least one ULP servicelayer message from the SET comprises: receiving SET service capabilitiesfrom the SET; and requesting service from the SET that is consistentwith the SET service capabilities.
 8. The method of claim 7, wherein theSET service capabilities comprise positioning protocols supported by theSET and are received prior to transmitting at least one positioninglayer message to the SET.
 9. The method of claim 7, further comprisingtransmitting service capabilities of the SLP to the SET in response toreceipt of the SET service capabilities.
 10. The method of claim 7,further comprising receiving a service modification request from the SETwith service parameters that are modified with respect to the servicerequested from the SET.
 11. The method of claim 7, further comprisingtransmitting a service modification request to the SET with serviceparameters that are modified with respect to the service requested fromthe SET.
 12. The method of claim 10, further comprising determining aplurality of position estimates for the SET at a plurality of times,wherein the service modification request is received between positionestimates.
 13. The method of claim 11, further comprising determining aplurality of position estimates for the SET at a plurality of times,wherein the service modification request is transmitted between positionestimates.
 14. An apparatus comprising: at least one processorconfigured to: receive from a Secure User Plane Location (SUPL) agent arequest for at least one position estimate for a SUPL enabled terminal(SET); transmit at least one User plane Location Protocol (ULP) servicelayer message to the SET and receive at least one ULP service layermessage from the SET, wherein ULP service layer messages do not containany positioning related parameters except positioning protocolidentification and positioning protocol messages; transmit at least onepositioning layer message to the SET and receive at least onepositioning layer message from the SET, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; communicate with the SET to determine the atleast one position estimate for the SET; and send the at least oneposition estimate to the SUPL agent.
 15. The apparatus of claim 14,wherein the positioning layer messages are encapsulated within the ULPservice layer messages, wherein the ULP service layer messages do notcontain service layer parameters.
 16. The apparatus of claim 14, whereinthe positioning layer messages are encapsulated within the ULP servicelayer messages, wherein the ULP service layer messages contain servicelayer parameters.
 17. The apparatus of claim 14, wherein the positioningprotocol comprises LTE Positioning Protocol (LPP), Radio Resource LCSProtocol (RRLP), Radio Resource Control (RRC) or IS-801.
 18. Theapparatus of claim 14, wherein no positioning related parameters areprovided prior to requesting service from the SET.
 19. The apparatus ofclaim 14, wherein the at least one processor is configured to determinea position estimate for the SET for multiple reporting events.
 20. Theapparatus of claim 14, wherein the at least one processor is furtherconfigured to: receive SET service capabilities; and request servicefrom the SET that is consistent with the SET service capabilities. 21.The apparatus of claim 20, wherein the SET service capabilities comprisepositioning protocols supported by the SET and are received prior totransmitting at least one positioning layer message to the SET.
 22. Theapparatus of claim 20, wherein the at least one processor is furtherconfigured to transmit service capabilities of a SUPL Location Platform(SLP) to the SET in response to receipt of the SET service capabilities.23. The apparatus of claim 20, wherein the at least one processor isfurther configured to receive a service modification request from theSET with service parameters that are modified with respect to theservice requested from the SET.
 24. The apparatus of claim 20, whereinthe at least one processor is further configured to transmit a servicemodification request to the SET with service parameters that aremodified with respect to the service requested from the SET.
 25. Theapparatus of claim 23, wherein the at least one processor is furtherconfigured to determine a plurality of position estimates for the SET ata plurality of times, wherein the service modification request isreceived between position estimates.
 26. The apparatus of claim 24,wherein the at least one processor is further configured to determine aplurality of position estimates for the SET at a plurality of times,wherein the service modification request is transmitted between positionestimates.
 27. An apparatus comprising: means for receiving from aSecure User Plane Location (SUPL) agent a request for at least oneposition estimate for a SUPL enabled terminal (SET); means fortransmitting at least one User plane Location Protocol (ULP) servicelayer message to the SET and receiving at least one ULP service layermessage from the SET, wherein ULP service layer messages do not containany positioning related parameters except positioning protocolidentification and positioning protocol messages; means for transmittingat least one positioning layer message to the SET and receiving at leastone positioning layer message from the SET, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; and means for communicating with the SET todetermine the at least one position estimate for the SET; and means forsending the at least one position estimate to the SUPL agent.
 28. Acomputer-readable medium including program code stored thereon,comprising: program code to receive from a Secure User Plane Location(SUPL) agent a request for at least one position estimate for a SUPLenabled terminal (SET); program code to transmit at least one User planeLocation Protocol (ULP) service layer message to the SET and receive atleast one ULP service layer message from the SET, wherein ULP servicelayer messages do not contain any positioning related parameters exceptpositioning protocol identification and positioning protocol messages;program code to transmit at least one positioning layer message to theSET and receive at least one positioning layer message from the SET,wherein positioning layer messages conform to a positioning protocolthat does not contain any service related parameters; and program codeto communicate with the SET to determine the at least one positionestimate for the SET; and program code to send the at least one positionestimate to the SUPL agent.
 29. A method comprising: receiving from aSecure User Plane Location (SUPL) agent a request for at least oneposition estimate for a SUPL enabled terminal (SET); transmitting atleast one User plane Location Protocol (ULP) service layer message to aSUPL Location Platform (SLP) and receiving at least one ULP servicelayer message from the SLP, wherein ULP service layer messages do notcontain any positioning related parameters except positioning protocolidentification and positioning protocol messages; transmitting at leastone positioning layer message to the SLP and receiving at least onepositioning layer message from the SLP, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; communicating with the SLP to determine theat least one position estimate for the SET; and communicating with theSLP to provide to the SUPL agent at least one position estimate for theSET.
 30. The method of claim 29, wherein the positioning layer messagesare encapsulated within the ULP service layer messages, wherein the ULPservice layer messages do not contain service layer parameters.
 31. Themethod of claim 29, wherein the positioning layer messages areencapsulated within the ULP service layer messages, wherein the ULPservice layer messages contain service layer parameters.
 32. The methodof claim 29, wherein the positioning protocol comprises LTE PositioningProtocol (LPP), Radio Resource LCS Protocol (RRLP), Radio ResourceControl (RRC) or IS-801.
 33. The method of claim 29, further comprisingdetermining a position estimate for the SET for multiple reportingevents.
 34. The method of claim 29, wherein transmitting the at leastone ULP service layer message to the SLP and receiving the at least oneULP service layer message from the SLP comprises: transmitting SETservice capabilities to the SLP; receiving SLP service capabilities fromthe SLP; and transmitting a service request to the SLP that isconsistent with the SLP service capabilities.
 35. The method of claim34, further comprising transmitting a service modification request tothe SLP with service parameters that are modified with respect to theservice request transmitted to the SLP.
 36. The method of claim 34,further comprising receiving a service modification request from the SLPwith service parameters that are modified with respect to the servicerequest transmitted to the SLP.
 37. The method of claim 35, furthercomprising determining a plurality of position estimates for the SET ata plurality of times, wherein the service modification request istransmitted between position estimates.
 38. The method of claim 36,further comprising determining a plurality of position estimates for theSET at a plurality of times, wherein the service modification request isreceived between position estimates.
 39. An apparatus comprising: atleast one processor configured to: receive from a Secure User PlaneLocation (SUPL) agent a request for at least one position estimate for aSUPL enabled terminal (SET); transmit at least one User plane LocationProtocol (ULP) service layer message to a SUPL Location Platform (SLP)and receive at least one ULP service layer message from the SLP, whereinULP service layer messages do not contain any positioning relatedparameters except positioning protocol identification and positioningprotocol messages; transmit at least one positioning layer message tothe SLP and receive at least one positioning layer message from the SLP,wherein positioning layer messages conform to a positioning protocolthat does not contain any service related parameters; communicate withthe SLP to determine the at least one position estimate for the SET; andcommunicate with the SLP to provide to the SUPL agent at least oneposition estimate for the SET.
 40. The apparatus of claim 39, whereinthe positioning layer messages are encapsulated within the ULP servicelayer messages, wherein the ULP service layer messages do not containservice layer parameters.
 41. The apparatus of claim 39, wherein thepositioning layer messages are encapsulated within the ULP service layermessages, wherein the ULP service layer messages contain service layerparameters.
 42. The apparatus of claim 39, wherein the positioningprotocol comprises LTE Positioning Protocol (LPP), Radio Resource LCSProtocol (RRLP), Radio Resource Control (RRC) or IS-801.
 43. Theapparatus of claim 39, wherein the at least one processor is configuredto determine a position estimate for the SET for multiple reportingevents.
 44. The apparatus of claim 39, wherein the at least oneprocessor is further configured to: transmit SET service capabilities tothe SLP; receive SLP service capabilities from the SLP; and transmit aservice request to the SLP that is consistent with the SLP servicecapabilities.
 45. The apparatus of claim 44, wherein the at least oneprocessor is further configured to transmit a service modificationrequest to the SLP with service parameters that are modified withrespect to the service request transmitted to the SLP.
 46. The apparatusof claim 44, wherein the at least one processor is further configured toreceive a service modification request from the SLP with serviceparameters that are modified with respect to the service requesttransmitted to the SLP.
 47. The apparatus of claim 45, wherein the atleast one processor is further configured to determine a plurality ofposition estimates for the SET at a plurality of times, wherein theservice modification request is transmitted between position estimates.48. The apparatus of claim 46, wherein the at least one processor isfurther configured to determine a plurality of position estimates forthe SET at a plurality of times, wherein the service modificationrequest is received between position estimates.
 49. An apparatuscomprising: means for receiving from a Secure User Plane Location (SUPL)agent a request for at least one position estimate for a SUPL enabledterminal (SET); means for transmitting at least one User plane LocationProtocol (ULP) service layer message to a SUPL Location Platform (SLP)and receiving at least one ULP service layer message from the SLP,wherein the ULP service layer messages do not contain any positioningrelated parameters except positioning protocol identification andpositioning protocol messages; means for transmitting at least onepositioning layer message to the SLP and receiving at least onepositioning layer message from the SLP, wherein positioning layermessages conform to a positioning protocol that does not contain anyservice related parameters; means for communicating with the SLP todetermine the at least one position estimate for the SET; and means forcommunicating with the SLP to provide to the SUPL agent at least oneposition estimate for the SET.
 50. A computer-readable medium includingprogram code stored thereon, comprising: program code to receive from aSecure User Plane Location (SUPL) agent a request for at least oneposition estimate for a SUPL enabled terminal (SET); program code totransmit at least one User plane Location Protocol (ULP) service layermessage to a SUPL Location Platform (SLP) and receive at least one ULPservice layer message from the SLP, wherein ULP service layer messagesdo not contain any positioning related parameters except positioningprotocol identification and positioning protocol messages; program codeto transmit at least one positioning layer message to the SLP andreceive at least one positioning layer message from the SLP, whereinpositioning layer messages conform to a positioning protocol that doesnot contain any service related parameters; program code to communicatewith the SLP to determine the at least one position estimate for theSET; and program code to communicate with the SLP to provide to the SUPLagent at least one position estimate for the SET.